Skip to content

fix(CI): bootstrap.py no longer reuses a stale package database - #12341

Merged
mergify[bot] merged 1 commit into
haskell:masterfrom
zlonast:zlonast/bootstrap
Sep 12, 2026
Merged

fix(CI): bootstrap.py no longer reuses a stale package database#12341
mergify[bot] merged 1 commit into
haskell:masterfrom
zlonast:zlonast/bootstrap

Conversation

@zlonast

@zlonast zlonast commented Sep 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

fix: #12311

The package database is now deleted and recreated from scratch on every
bootstrap run, making the script idempotent with respect to a dirty or
polluted _build. Additionally, the Bootstrap workflow now hashes the
.cabal files of the local packages into its cache key, so caches are no
longer shared between branches that build different versions of the local
packages.

  $ python3 bootstrap/bootstrap.py --bootstrap-sources bootstrap-sources.tar.gz
+ Deleting stale package database _build/packages.conf
  Creating package database _build/packages.conf
  Using ...

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

@ffaf1 ffaf1 mentioned this pull request Sep 9, 2026
Open
54 tasks
ulysses4ever
ulysses4ever approved these changes Sep 9, 2026
View reviewed changes

@ulysses4ever ulysses4ever left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me.

@zlonast zlonast added the merge me Tell Mergify Bot to merge label Sep 9, 2026
@mergify mergify Bot added the ready and waiting Mergify is waiting out the cooldown period label Sep 9, 2026
@haskell haskell deleted a comment from humh25 Sep 10, 2026
@mergify mergify Bot added merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days queued labels Sep 11, 2026
@mergify

mergify Bot commented Sep 11, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • ✅ Entered queue — 2026-09-11 12:23 UTC · Rule: default · triggered by rule Put pull requests in the rebase+merge queue
  • ❌ Checks failed · on draft merge queue: checking #12341 on master (36d21f8) #12347
  • 🚫 Left the queue — 2026-09-11 14:02 UTC · at 72fa62f4bebe4e2d467b72396b627baff40a87d8

This pull request spent 1 hour 38 minutes 50 seconds in the queue, including 1 hour 27 minutes 31 seconds running CI.

Waiting for any of
  • check-neutral = Validate post job
  • check-skipped = Validate post job
  • check-success = Validate post job
All conditions
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

Reason

The merge conditions cannot be satisfied due to failing checks

  • Doctest Cabal
  • Meta checks
  • docs/readthedocs.org:cabal
  • Validate post job
  • fourmolu
  • hlint
  • Bootstrap post job
  • whitespace
  • Check sdist post job
  • Changelogs

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

@mergify mergify Bot mentioned this pull request Sep 11, 2026
Closed
84 tasks
@mergify mergify Bot added dequeued and removed queued labels Sep 11, 2026
@zlonast

zlonast commented Sep 11, 2026

Copy link
Copy Markdown
Collaborator Author

@mergify queue

@mergify

mergify Bot commented Sep 11, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 1 hour 51 minutes 5 seconds in the queue, including 1 hour 39 minutes 16 seconds running CI.

Waiting for any of
  • check-neutral = Validate post job
  • check-skipped = Validate post job
  • check-success = Validate post job
All conditions
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

Reason

The merge conditions cannot be satisfied due to failing checks

  • Doctest Cabal
  • Meta checks
  • docs/readthedocs.org:cabal
  • Validate post job
  • fourmolu
  • hlint
  • Bootstrap post job
  • whitespace
  • Check sdist post job
  • Changelogs

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

@mergify mergify Bot added queued and removed dequeued labels Sep 11, 2026
@mergify mergify Bot mentioned this pull request Sep 11, 2026
Closed
84 tasks
@mergify mergify Bot added dequeued and removed queued labels Sep 11, 2026
@zlonast

zlonast commented Sep 12, 2026

Copy link
Copy Markdown
Collaborator Author

@Mergifyio queue

@mergify

mergify Bot commented Sep 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 1 hour 44 minutes 26 seconds in the queue, including 1 hour 33 minutes 15 seconds running CI.

Waiting for any of
  • check-neutral = Validate post job
  • check-skipped = Validate post job
  • check-success = Validate post job
All conditions
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

Reason

The merge conditions cannot be satisfied due to failing checks

  • Doctest Cabal
  • Meta checks
  • docs/readthedocs.org:cabal
  • Validate post job
  • fourmolu
  • hlint
  • Bootstrap post job
  • whitespace
  • Check sdist post job
  • Changelogs

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

@mergify mergify Bot added queued and removed dequeued labels Sep 12, 2026
@mergify mergify Bot mentioned this pull request Sep 12, 2026
Closed
84 tasks
@mergify mergify Bot added dequeued and removed queued labels Sep 12, 2026
@zlonast

zlonast commented Sep 12, 2026

Copy link
Copy Markdown
Collaborator Author

@mergify queue

@mergify

mergify Bot commented Sep 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 2 hours 5 minutes 55 seconds in the queue, including 1 hour 54 minutes 45 seconds running CI.

Required conditions to merge
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

@mergify mergify Bot added queued and removed dequeued labels Sep 12, 2026
@mergify mergify Bot mentioned this pull request Sep 12, 2026
Closed
84 tasks
@mergify
mergify Bot merged commit a7e1439 into haskell:master Sep 12, 2026
129 of 131 checks passed
@mergify mergify Bot removed the queued label Sep 12, 2026
@zlonast
zlonast deleted the zlonast/bootstrap branch September 12, 2026 08:26
@zlonast

zlonast commented Sep 12, 2026

Copy link
Copy Markdown
Collaborator Author

@mergify backport 3.18

@mergify

mergify Bot commented Sep 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

backport 3.18

✅ Backports have been created

Details

@mergify mergify Bot mentioned this pull request Sep 12, 2026
Merged
2 tasks
mergify Bot added a commit that referenced this pull request Sep 12, 2026
@mergify
Merge pull request #12353 from haskell/mergify/bp/3.18/pr-12341
f3cd692 
Backport #12341: fix(CI): bootstrap.py no longer reuses a stale package database
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ulysses4ever ulysses4ever ulysses4ever approved these changes
@ffaf1 ffaf1 ffaf1 approved these changes
@Mikolaj Mikolaj Awaiting requested review from Mikolaj

Assignees

No one assigned

Labels

attention: needs-backport 3.18 attention: needs-review merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge ready and waiting Mergify is waiting out the cooldown period

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Bootstrap: stale CI cache makes bootstrap.py mix Cabal-syntax-3.18.1.0 and Cabal-syntax-3.19.0.0 in the bootstrap package DB

3 participants

@zlonast @ulysses4ever @ffaf1